Apparatus and method for processing call and message-related events in a wireless terminal

ABSTRACT

A character agent function is added to a wireless terminal and an avatar user interface (UI) for generating and processing an event is expressed when an event occurs in the wireless terminal, such that call and message-related events occurring in the wireless terminal can be expressed through the character agent function.

PRIORITY

This application is a continuation of U.S. patent application Ser. No.13/567,981, filed on Aug. 6, 2012, which is a continuation of U.S.patent application Ser. No. 12/314,761, filed on Dec. 16, 2008, now U.S.Pat. No. 8,254,899, which is a division of U.S. patent application Ser.No. 11/311,357, filed on Dec. 20, 2005, now U.S. Pat. No. 7,474,903,which claims the benefit under 35 U.S.C. §119(a) of two Koreanapplications, both entitled “Apparatus and Method for Processing Calland Message-Related Events in a Wireless Terminal,” filed in the KoreanIntellectual Property Office on Dec. 20, 2004 and Dec. 6, 2005, andassigned Serial Nos. 2004-109023 and 2005-118103, respectively, theentire contents of all of said prior applications being herebyincorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to an agent apparatus and methodfor use in a wireless terminal. More particularly, the present inventionrelates to an apparatus and method for implementing a character agentfunction, and processing a call and message-related events in a wirelessterminal.

2. Description of the Related Art

Conventionally, a wireless terminal is a portable device carried by auser, and the wireless terminal's representative device is a wirelessphone. The wireless phone can serve various supplementary functions aswell as a basic phone function. Wireless phones with the supplementaryfunctions may be a camcorder phone with a camera, television (TV) phonethrough which TV can be watched, Moving Picture Experts Group (MPEG)layer 3 (MP3) through which an MP3 music file can be listened to,digital multimedia broadcasting (DMB) phone through which satellitebroadcasting and/or terrestrial broadcasting programs can be watched,and the like. Accordingly, products with supplementary functions capableof processing multimedia data are widely used as the current wirelessphones.

The wireless terminals with various supplementary functionsconventionally include a liquid crystal display (LCD). Various displaymethods for effectively displaying information on a display unit of theLCD are being developed such that a user can easily recognize varioussupplementary functions, and states of a wireless terminal. The wirelessterminals are being developed such that various types of user data canbe displayed. Currently, user data displayed in the wireless terminalsare mainly configured by visual image data such as photo data, characterimages, animations, and the like. Avatar image data can also be includedin the user data, and a need exists for wireless terminals using theavatar image data.

SUMMARY OF THE INVENTION

An aspect of embodiments of the present invention is to address at leastthe above problems and/or disadvantages and to provide at least theadvantages described below. Accordingly, an aspect of embodiments of thepresent invention to provide an apparatus and method that can expresscall and message-related events through a character agent function whenthe events occur in a wireless terminal.

It is another object of an exemplary embodiment of the present inventionto provide an apparatus and method that can analyze call andmessage-related events occurring in a wireless terminal to select andexpress a character user interface (UI) provided in an optimumspecialist.

It is yet another object of an exemplary embodiment of the presentinvention to provide an apparatus and method for expressing call andmessage-related events in a wireless terminal that can select acharacter user interface (UI) to express a call and message-relatedevent occurring in the wireless terminal under control of a controller.

In accordance with an aspect of an exemplary embodiment of the presentinvention, there is provided an apparatus for processing call andmessage-related events in a wireless terminal, comprising: a memory forstoring character user interface (UI) images based on call andmessage-related events; an agent collection unit for collecting the calland message-related events occurring in the wireless terminal andgenerating an event message for identifying an occurred call andmessage-related event; an agent control unit, provided with a pluralityof specialists for processing the call and message-related events, forselecting a specialist mapped to the event message from the plurality ofspecialists, selecting and outputting a character UI identifier (ID)based on a call and message-related event of the selected specialist,and processing user feedback information for an associated event inresponse to the feedback information received from a user; and an agentexpression unit for outputting a character and text mapped to the calland message-related event and the feedback information.

In accordance with another aspect of an exemplary embodiment of thepresent invention, there is provided a method for processing call andmessage-related events in a wireless terminal, comprising the steps of:analyzing call and message-related records of an associated contactperson when a call and message-related contact event occurs; andexpressing an alarm event mapped to a result of analyzing the call andmessage-related records using a character and text.

In accordance with yet another aspect of an exemplary embodiment of thepresent invention, there is provided a method for processing call andmessage-related events in a wireless terminal, comprising the steps of:determining a type of an alarm event when the alarm event occurs;analyzing call and message-related records according to the occurredalarm event; and expressing a character and text mapped to a result ofanalyzing the call and message-related records.

Other objects, advantages, and salient features of the invention willbecome apparent to those skilled in the art from the following detaileddescription, which taken in conjunction with the annexed drawings,discloses exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features, and advantages of certainexemplary embodiments of the present invention will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram illustrating a structure of a wirelessterminal in accordance with an exemplary embodiment of the presentinvention;

FIG. 2 is a functional block diagram illustrating a controller of thewireless terminal in accordance with an exemplary embodiment of thepresent invention;

FIG. 3 is a flowchart illustrating an operation for setting up arelation to a contact person who has made call/message-related contact(or registering the person in a specific group) using a character agentin accordance with an exemplary embodiment of the present invention;

FIG. 4 is a flowchart illustrating an operation for notifying that asubstantial number of a call/message-related contact has been made usinga character agent in accordance with an exemplary embodiment of thepresent invention;

FIG. 5 is a flowchart illustrating an operation for setting up arelation to a contact person who has made continuouscall/message-related contact (or registering the person in a specificgroup) using a character agent in accordance with an exemplaryembodiment of the present invention;

FIG. 6 is a flowchart illustrating an operation for setting up an alarmfor recommending contact with a specific person who has previously maderegular contact but has not recently made contact using a characteragent in accordance with an exemplary embodiment of the presentinvention;

FIG. 7 is a flowchart illustrating an operation for recommending contactwith a specific person who has previously made regular contact but hasnot recently made contact using a character agent in accordance with anexemplary embodiment of the present invention;

FIG. 8 is a flowchart illustrating an operation for recommending contactwith a specific person who has generally made little contact using acharacter agent in accordance with an exemplary embodiment of thepresent invention;

FIG. 9 is a flowchart illustrating an operation for recommending contactwith a specific person of a specific group who has recently made littlecontact using a character agent in accordance with an exemplaryembodiment of the present invention;

FIG. 10 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this week using a character agent inaccordance with an exemplary embodiment of the present invention;

FIG. 11 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this month using a character agentin accordance with an exemplary embodiment of the present invention;

FIG. 12 is a flowchart illustrating an operation for giving notificationindicating if some work on today's TO-DO list has been completed using acharacter agent in accordance with an exemplary embodiment of thepresent invention;

FIG. 13 is a flowchart illustrating an operation for giving notificationindicating if some work on yesterday's TO-DO list has been completedusing a character agent in accordance with an exemplary embodiment ofthe present invention;

FIG. 14 is a flowchart illustrating an operation for setting up arelation to a contact person who has made call/message-related contact(or registering the person in a specific group) in the wireless terminalin accordance with an exemplary embodiment of the present invention;

FIG. 15 is a flowchart illustrating an operation for notifying that asubstantial number of a call/message-related contact has been made inthe wireless terminal in accordance with an exemplary embodiment of thepresent invention;

FIG. 16 is a flowchart illustrating an operation for setting up arelation to a contact person who has made continuouscall/message-related contact (or registering the person in a specificgroup) in the wireless terminal in accordance with an exemplaryembodiment of the present invention;

FIG. 17 is a flowchart illustrating an operation for setting up an alarmfor recommending contact with a specific person who has previously maderegular contact but has not recently made contact in the wirelessterminal in accordance with an exemplary embodiment of the presentinvention;

FIG. 18 is a flowchart illustrating an operation for recommendingcontact with a specific person who has previously made regular contactbut has not recently made contact in the wireless terminal in accordancewith an exemplary embodiment of the present invention;

FIG. 19 is a flowchart illustrating an operation for recommendingcontact with a specific person who has generally made little contact inthe wireless terminal in accordance with an exemplary embodiment of thepresent invention;

FIG. 20 is a flowchart illustrating an operation for recommendingcontact with a specific person of a specific group who has recently madelittle contact in the wireless terminal in accordance with an exemplaryembodiment of the present invention;

FIG. 21 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this week in the wireless terminalin accordance with an exemplary embodiment of the present invention;

FIG. 22 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this month in the wireless terminalin accordance with an exemplary embodiment of the present invention;

FIG. 23 is a flowchart illustrating an operation for giving notificationindicating if some work on today's TO-DO list has been completed in thewireless terminal in accordance with an exemplary embodiment of thepresent invention;

FIG. 24 is a flowchart illustrating an operation for giving notificationindicating if some work on yesterday's TO-DO list has been completed inthe wireless terminal in accordance with an exemplary embodiment of thepresent invention;

FIGS. 25A-25D illustrates exemplary screens in an operation forrecommending the setup of a relation to a specific person who hasrecently made much contact in accordance with an exemplary embodiment ofthe present invention;

FIGS. 26A-26D illustrates exemplary screens in an operation fornotifying that a substantial number of a call/message-related contactwith a specific person has been recently made in accordance with anexemplary embodiment of the present invention;

FIGS. 27A-27D illustrates exemplary screens in an operation forrecommending the setup of a relation to a specific person who has madecontinuous contact in accordance with an exemplary embodiment of thepresent invention;

FIGS. 28A-28D illustrates exemplary screens in an operation forrecommending contact with a specific person who has previously maderegular contact but has not recently made contact in accordance with anexemplary embodiment of the present invention;

FIGS. 29A-29D illustrates exemplary screens in an operation forrecommending contact with a specific person who has generally madelittle contact in accordance with an exemplary embodiment of the presentinvention;

FIGS. 30A-30D illustrates exemplary screens in an operation forrecommending contact with a specific person of a specific group who hasrecently made little contact in accordance with an exemplary embodimentof the present invention;

FIG. 31 illustrates exemplary screens in an operation for givingnotification of the number of calls/messages for this week in accordancewith an exemplary embodiment of the present invention;

FIG. 32 illustrates exemplary screens in an operation for givingnotification of the number of calls/messages for this month inaccordance with an exemplary embodiment of the present invention;

FIGS. 33A-33C illustrates exemplary screens in an operation for givingnotification indicating if some work on today's TO-DO list has beencompleted in accordance with an exemplary embodiment of the presentinvention; and

FIGS. 34A-34C illustrates exemplary screens in an operation for givingnotification indicating if some work on yesterday's TO-DO list has beencompleted in accordance with an exemplary embodiment of the presentinvention.

Throughout the drawings, the same drawing reference numerals will beunderstood to refer to the same elements, features, and structures.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The matters defined in the description such as a detailed constructionand elements are provided to assist in a comprehensive understanding ofthe embodiments of the invention. Accordingly, those of ordinary skillin the art will recognize that various changes and modifications of theembodiments described herein can be made without departing from thescope and spirit of the invention. Also, descriptions of well-knownfunctions and constructions are omitted for clarity and conciseness. Inthe following description, specific details, such as types of events andinformation necessary for agent expression are provided for a betterunderstanding of the present invention. An alarm event may be a timerevent. The timer event occurs when a set occurrence time is reached.Hereinafter, an alarm and an alarm event may be used in the samemeaning.

FIG. 1 is a block diagram illustrating a structure of a wirelessterminal for expressing a character agent according to an eventoccurring therein in accordance with an exemplary embodiment of thepresent invention. Referring to FIG. 1, a radio frequency (RF)communication unit 21 performs a wireless communication function of thewireless terminal. The RF communication unit 21 includes an RFtransmitter for up converting and amplifying a frequency of a signal tobe transmitted, and RF receiver for low noise amplifying a receivedsignal and down converting a frequency of the received signal. A keyinput unit 25 is provided with keys for inputting number and letterinformation and function keys for setting various functions. Moreover,the key input unit 25 is provided with keys for controlling a characteragent on an event-by-event basis in accordance with an exemplaryembodiment of the present invention.

A memory 23 can be configured by program and data memories. The programmemory stores programs for processing a call of the wireless terminaland for controlling agent expression for events occurring in accordancewith an exemplary embodiment of the present invention. The data memorytemporarily stores data generated in operation. Moreover, the datamemory is provided with a character memory for storing character imagesfor agent expression in accordance with an exemplary embodiment of thepresent invention. The character memory can operate with a file system,and can have an index of a character-by-character memory (or filesystem). The character memory can be configured in various forms forenabling operations, facial expressions, and object representations ofcharacter components. Character information can be stored in thecharacter memory according to an agent expression form. A text memoryfor storing text for agent expression is provided. The text memory canstore associated content according to an occurred event or feedback.Registered TO-DO information, phone number (phone book) listinformation, and occurred events are stored on a type-by-type basis.

The controller 100 performs a function for controlling the overalloperation of the wireless terminal. Moreover, the controller 100 isprovided with a modulator-demodulator (MODEM) formodulating/demodulating a signal and a coder-decoder (CODEC) forcoding/decoding a signal. As a result, the controller 100 performs afunction for coding and modulating a signal to be transmitted and afunction for demodulating and decoding a received signal. Here, thecontroller 100 may be a mobile station modem (MSM) chip. The controller100 controls operations of communication mode, camera mode, andbroadcasting reception mode in response to mode selected by a user. Adata processor is independently configured to separate the MODEM andCODEC from the controller 100. The data processor can be placed betweenthe RF communicator 21 and the controller 100. In accordance with anexemplary embodiment of the present invention, the controller 100collects an event according to the operation of the wireless terminal,controls an agent according to the collected event, and expresses aresult of processing and state of the event using an agent. Here, theagent expression can be displayed after an associated character and textare selected from the memory 23. An associated character and text can bedisplayed according to a feedback.

At the time of the user's camera mode selection, a camera 35 is startedby the controller 100 and generates an image capture signal in thecamera mode. An image processor 37 scales the image capture signal fromthe camera 35 according to a size of a display unit 27 in the cameramode, and encodes and stores the image capture signal in a storage modeaccording to a set scheme. In a mode for reproducing received or storedimage data, the image processor 37 performs a function for decodingencoded image data.

In the broadcasting reception mode, a tuner 31 selects and receives abroadcast signal of a channel set under control of the controller 100. Abroadcast processor 33 demodulates and decodes the broadcast signal ofthe selected channel, and outputs the demodulated and decoded imagesignal to the display unit 27. An audio signal is output to an audioprocessor 29. Here, the broadcast signal may be a satellite broadcastsignal or a terrestrial broadcast signal.

Under the control of the controller 100, the display unit 27 can displaymenus according to the operation of the wireless terminal. When an eventoccurs, the display unit 27 displays an output character mapped to theevent. Moreover, the display unit 27 displays an image signal outputfrom the image processor 37 or the broadcast processor 33 in the cameramode or broadcasting reception mode.

Under the control of the controller 100, the audio processor 29processes an audio signal generated in the communication mode. Under thecontrol of the image processor 37, the audio processor 29 processes anaudio signal generated during an image capture operation in the cameramode. The audio processor 29 processes a broadcast audio signal receivedunder the control of the broadcast processor 33 in the broadcastingreception mode.

A structure for processing the camera signal and/or broadcast signal canbe omitted from the wireless terminal with the above-describedstructure. In this case, a character agent function for an event can beperformed in accordance with an exemplary embodiment of the presentinvention. In the following description, it is assumed that thecharacter is an avatar. Accordingly, character agent control for anevent of the wireless terminal will be described as avatar agentcontrol, but can be equally applied for all images as well as theavatar.

FIG. 2 is a functional block diagram illustrating a controller of thewireless terminal in accordance with an exemplary embodiment of thepresent invention. An example of the functional block configuration asillustrated in FIG. 2 is disclosed in Korean Patent Application SerialNo. 2004-78470, entitled “Intelligent Terminal Using an ArtificialIntelligence Agent”, filed by Kim Jaeho, et al. The followingdescription will be given with reference to content disclosed in KoreanPatent Application Serial No. 2004-78470. To implement the presentinvention, the controller 100 may control a single agent system withoutfunctional blocks such as an event collection unit, event delivery unit,agent control unit, and agent expression unit.

Referring to FIG. 2, the event collection unit 110 performs a functionfor collecting events occurring in the wireless terminal. Here, theevents include all events of the wireless terminal such as acommunication event of the wireless terminal, event occurring in thewireless terminal itself, event occurring according to the user'srequest, and event occurring when a multimedia function of the wirelessterminal is performed. That is, the events collected by the eventcollection unit 110 are events defined in the wireless terminal. Theevent collection unit 110 generates an event message for identifying anoccurred event, and provides the event message to the event deliveryunit 120.

The event delivery unit 120 performs a function for delivering the eventmessage received from the event collection unit 110 to an associatedclient. In accordance with an exemplary embodiment of the presentinvention, it is assumed that the event delivery unit 120 delivers theevent message only to the agent control unit 130. When a differentcomponent makes an event message delivery request, the event message canbe delivered to the different component. Moreover, the event deliveryunit 120 receives user-defined events undefined in the wireless terminalas well as the events received from the event collector 100 and deliversthe received events to the agent control unit 130. Here, theuser-defined events as described above are referred to as applicationevents. The application events may occur in games, other applicationprograms, and web service programs.

When receiving an event message from the event delivery unit 120, theagent control unit 130 stores the received event message in an internalbuffer, and analyzes the event message to set a user interface (UI) suchthat an associated character agent can be expressed. Here, the eventdelivered from the event delivery unit 120 may be events of the wirelessterminal (for example, events received from the event collection unit110) and application events. In the following, a description is focusedon the agent expression for an event received from the event collectionunit 110. The agent control unit 130 is provided with a plurality ofspecialists. The agent control unit 130 controls these specialists,selects a specialist mapped to an occurred event, and performs an agentcontrol function.

When an event is received, the agent control unit 130 notifies suitablespecialists of event occurrence according to the received event, andsends a UI request to the agent expression unit 140 such that agentexpression of the finally selected specialist can be displayed. Inresponse to feedback information of the user received from the agentexpression unit 140, the user feedback information for an associatedevent is processed.

The agent expression unit 140 displays the character expression for anassociated event according to agent UI information output from the agentcontrol unit 130. At this time, the agent expression unit 140 manages aplurality of avatar UIs to be displayed on the display unit 27. Theagent control unit 130 performs a control operation such that an avatarmapped to requested UI information can be displayed. When the usergenerates the feedback information in a state in which the avatar hasbeen displayed according to the occurred event, the agent expressionunit 140 sends the received feedback information to the agent controlunit 130. The agent control unit 130 performs agent control according tothe user feedback information received from the agent expression unit140.

When only the events of the wireless terminal collected by the eventcollection unit 110 are processed in the structure of FIG. 2, the eventdelivery unit 120 can be omitted. Here, the internal buffer of the agentcontrol unit 130 is referred to as a blackboard.

Next, the structure and operation of the agent control unit 130 will bedescribed in more detail. The agent control unit 130 includes aplurality of specialists for receiving a call according to an eventtype, performing a preset special task, and outputting a task result. Ablackboard stores various information including information of eventmessages. A supervisor selects one specialist when a plurality ofspecialists output valid results. An avatar quotient memory stores anavatar quotient according to an occurred event. A specialist managerselects associated specialists from a list of event-by-event specialistsat the time of event occurrence and controls an agent according to anevent.

The specialists make a contribution to solving a problem and havespecialty for defined parts. The specialists record a solution of anintermediate step in the blackboard and also express a priority and userpreference for the solution of the intermediate step. The specialistsidentify a state of the blackboard, make a request for computing thepriority and user preference, and record the solution of theintermediate step in the blackboard.

The blackboard is a working environment and information space forcommunication between the specialists. Basically, the specialists canrecord the solution of the intermediate step. Advantages of a pattern ofthe blackboard 330 are as follows. First, many specialists of differenttypes can be easily integrated. Second, the specialists can beindependently modularized and developed because the specialists seldomaffect each other. Third, flexibility is provided for many variations,such as a change of a specialist algorithm or an addition of a newspecialist.

When at least two specialists are selected in relation to one event, thespecialist manager requests that the supervisor select a specialist mostclosely related to the received event. The supervisor analyzes data ofthe blackboard, a basically designated priority according to an eventand user preference, thereby selecting the specialist with the closestrelation.

An internal quotient of an avatar is varied according to an agentfunction and various events occurring in the wireless terminal and thefeedback information of the user. Also, many application events capableof using the avatar quotient affect the avatar quotient. As the internalquotient is varied, an avatar interface is varied. As a period of timeelapses, the appearance in which the avatar is brought up is viewed.This is a growth concept of the avatar. In accordance with an exemplaryembodiment of the present invention, the avatar growth is introducedinto the wireless terminal based on an artificial intelligence (AI)agent system. For this, the wireless terminal proposes and reports manyactions to the user on the basis of various events occurring in thewireless terminal. Accordingly, the user can use the terminal moreeffectively and enjoyably. On the basis of these events and the user'sfeedback action, an avatar image and text are varied, and the avatarquotient is varied.

Table 1 shows concrete cases in accordance with an exemplary embodimentof the present invention. Table 1 shows event use cases, caseclassification, event determination times, action (processing) times ofspecialists, the number of occurrences, times, event parameters(necessary information), conditions, UI text, user options, and so on.Other cases can be added to the above cases or some cases can bedeleted.

TABLE 1 Info necessary for ID Use Case Class controller UI Text Option 4Make the praise CALL/MESSAGE AP_PHONE_ANSWER/ You have made Yes/No andrecommend AP_PHONE_SEND/ much contact relation setup AP_SMS_SEND/ with[Name]. when the number AP_SMS_READ/ Would you like to of calls/messagesContactID/Number set up a relation? for contact with a specific personis large. 5 Make the praise CALL/MESSAGE AP_PHONE_ANSWER/ You have Yes/when the number AP_PHONE_SEND/ recently made Really?/ of calls/messagesAP_SMS_SEND/ much contact Cut it for contact with a AP_SMS_READ/ with[Name]. It off! specific person is ContactID/Number seems that yoularge. have a special relation to [Name]. 6 Recommend CALL/MESSAGEAP_PHONE_ANSWER/ A relation to Yes/No relation setup for aAP_PHONE_SEND/ [Name] is not set number when AP_SMS_SEND/ up. Would youregular contact has AP_SMS_READ/ like to set up a been made butContactID/Number relation to relation to the [Name] at this number isnot set time? up. 7 Identify a contact CALL/MESSAGE AP_PHONE_ANSWER/ Youhave Call/Message/No person who has AP_PHONE_SEND/ recently maderecently made little AP_SMS_SEND/ little contact with contact andAP_SMS_READ/ [Name]. Would recommend call ContactID/Number you like tocall (or message)- [Name] for related contact. greeting? 8 Identify acontact CALL/MESSAGE AP_PHONE_ANSWER/ You have made Call/Message/Noperson who has AP_PHONE_SEND/ little contact with generally madeAP_SMS_SEND/ [Name]. Would little contact and AP_SMS_READ/ you like tocall recommend call ContactID/Number [Name]? (or message)- relatedcontact. 10 Recommend (call CALL/MESSAGE AP_PHONE_ANSWER/ You have notCall/Message/No or message- AP_PHONE_SEND/ made contact related) contactAP_SMS_SEND/ with [Name] of with a contact AP_SMS_READ/ [Group]. Wouldperson of a group ContactID/Number you like to call who has not made[Name]? contact for a long time. 39 Show a call CALL/MESSAGE (The numberof OK duration time and calls and the the number of number of messagesfor this messages are week on Saturday, shown.) The compare number ofinformation of this calls/messages week with that of has been last week,and increased/decreased show an for this week increased/decreased ascompared with number of calls last week. (pattern analysis). 40 Show acall CALL/MESSAGE (The number of OK duration time and calls and the thenumber of number of messages for this messages are week at the end ofshown.) The the month, and number of show the calls/messagesincreased/decreased has been number of calls increased/decreased ascompared with for this month that of last week. as compared with lastmonth. 33 Ask if some work TO- Some work on Yes/No on the TO-DO list DOthe TO-DO list has been has not been completed at night completed. whenit is still Would you like to undone. check it? 34 Ask if some work TO-There remains Yes/No on the TO-DO list DO some work that has been shouldbe done completed when it yesterday. Would is still undone at you liketo check morning. it?

An operation for processing call and message-related contact events in awireless terminal in accordance with features of the present inventionwill be described. The contact events to be described below indicateoutgoing call (or phone call) transmission and/or incoming call (orphone call) reception, and message transmission and/or messagereception.

FIG. 3 is a flowchart illustrating an operation for setting up arelation to a contact person who has made a call/message-related contact(or registering the person in a specific group) using a character agentin accordance with an exemplary embodiment of the present invention.

Referring to FIG. 3, an event collection unit (not illustrated) collectsa call (or phone call) and message-related contact events when the call(or phone call) and message-related contact events occur. The call (orphone call) and message-related contact events may be phone calltermination events, incoming phone call reception events, outgoing phonecall transmission events, message reception events, and/or messagetransmission events. Then, the call (or phone call) and message-relatedcontact events are provided to an event delivery unit (not illustrated).The event delivery unit (not illustrated) provides the events to aspecialist manager of an agent control unit in step 1602. The specialistmanager stores the call (or phone call) and message-related contactevents in a blackboard in step 1604. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen the call (or phone call) and message-related contact events occurin step 1606. Then, the specialist manager calls the specialists in step1608. (FIG. 3 illustrates an example in which a specialist of Identifier(ID) 4 is called.)

Among the called specialists, the specialist of ID 4 is provided torecommend relation setup (or group registration) when a contact personhas recently made frequent contact, but a relation to the contact person(or his/her phone number) has not been set up or has not been registeredin a specific group. In step 1610, call (or phone call) and/ormessage-related contact records for one recent week are analyzed. Then,a determination is made as to whether a frequent call (or phone call)and/or message-related contact with the contact person (or his/her phonenumber) has been made at least a threshold number of times (for example,at least three times) for a predetermined period (for example, onerecent week). If frequent contact with an associated contact person hasnot been made, the operation proceeds to step 1614 to return the ‘NO’signal to the specialist manager. However, if frequent contact with theassociated contact person has been made, the operation proceeds to step1616. In step 1616, a determination is made as to whether a relation tothe contact person (or his/her phone number) has been set up (or thecontact person (or his/her phone number) has been registered in aspecific group). If the relation setup (or group registration) has beenmade, the operation proceeds to step 1618 to return the ‘NO’ signal tothe specialist manager. However, if a relation to the contact person (orhis/her phone number) has not been set up or has not been registered ina specific group, the operation proceeds to step 1620 to return the‘YES’ signal to the specialist manager.

When a called specialist makes the return, the specialist managerprovides a supervisor with an ID of the specialist returning the ‘YES’signal (for example, Specialist ID 4 of FIG. 3) in step 1622. Then, thesupervisor identifies priorities of associated specialists or identifiesthe execution of an associated specialist when the number of specialistsreturning ‘YES’ is one in step 1624. In step 1626, the supervisor sends,to the specialist manager, a result of the identification for thehighest priority specialist or the execution of the associatedspecialist. Then, the specialist manager identifies a UI ID of thehighest priority specialist or the specialist to be executed in step1628 and sends the identified UI ID to an agent expression unit in step1630. In step 1632, the agent expression unit expresses an associatedUI. When the specialist manager sends the UI ID to the agent expressionunit, information of an associated contact person can also be sent.

When this agent expression unit expresses a UI, for example, a UI mappedto Specialist ID 4, text for recommending the setup of a relation (orgroup) for an associated contact person (or his/her phone number) of acall (or phone call) and/or message can be included and expressed asillustrated in FIG. 25A. When an image and text for setting a characterwith a happy expression and/or a relation (or group) type are expressedand the relation (or group) is set according to the user's feedback asillustrated in FIG. 25B, a character with a happy expression and/or textindicating that the associated contact person (or his/her phone number)will be registered are expressed as illustrated in FIG. 25C or acharacter with a sad expression and/or text indicating that theassociated contact person (or his/her phone number) will not beregistered are expressed as illustrated in FIG. 25D. When apredetermined time elapses or a predetermined key is input, theexpressed character and/or text disappear. The information of thecontact person includes a phone number and ID of the contact person whohas made the call and/or message-related contact.

FIG. 4 is a flowchart illustrating an operation for notifying asubstantial number of a call/message-related contact that has been madeusing a character agent in accordance with an exemplary embodiment ofthe present invention.

Referring to FIG. 4, an event collection unit (not illustrated) collectsa call (or phone call) and message-related contact events when the call(or phone call) and message-related contact events occur. The call (orphone call) and message-related contact events may be phone calltermination events, incoming phone call reception events, outgoing phonecall transmission events, message reception events, and/or messagetransmission events. Then, the call (or phone call) and message-relatedcontact events are provided to an event delivery unit (not illustrated).The event delivery unit (not illustrated) provides the events to aspecialist manager of an agent control unit in step 1702. The specialistmanager stores the call (or phone call) and message-related contactevents in a blackboard in step 1704. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen the call (or phone call) and message-related contact events occurin step 1706. Then, the specialist manager calls the specialists in step1708. (FIG. 4 illustrates an example in which a specialist of ID 5 iscalled.)

Among the called specialists, the specialist of ID 5 is provided tonotify that a substantial number of contacts with a contact person thathas been recently made when a substantial number of a call (or phonecall) and/or message-related contact with the contact person (or his/herphone number) has been recently made. In step 1712, the call (or phonecall) and/or message-related contact records for one recent week areanalyzed. Then, a determination is made as to whether the substantialnumber of a call (or phone call) and/or message-related contact with thecontact person (and his/her phone number) has been made at least athreshold number of times (for example, at least five times) for apredetermined period (for example, one recent week) in step 1714. If thesubstantial number of contacts with an associated contact person has notbeen made, the operation proceeds to step 1716 to return the ‘NO’ signalto the specialist manager. However, if the substantial number ofcontacts with the associated contact person has been made, the operationproceeds to step 1718 to return the ‘YES’ signal to the specialistmanager.

When a called specialist makes the return, the specialist managerprovides a supervisor with an ID of the specialist returning the ‘YES’signal (for example, Specialist ID 5 of FIG. 4) in step 1720. Then, thesupervisor identifies priorities of associated specialists or identifiesthe execution of an associated specialist when the number of specialistsreturning ‘YES’ is one in step 1722. In step 1724, the supervisor sends,to the specialist manager, a result of the identification for thehighest priority specialist or the execution of the associatedspecialist. Then, the specialist manager identifies a UI ID of thehighest priority specialist or the specialist to be executed in step1726 and sends the identified UI ID to an agent expression unit in step1728. In step 1730, the agent expression unit expresses an associatedUI. When the specialist manager sends the UI ID to the agent expressionunit, information of an associated contact person can also be sent.Along with the information of the associated contact person, textindicating that a substantial number of a call/message-related contactwith the associated contact person has been made can be expressed asillustrated in FIG. 26A. In response to the user's feedback, a characterand/or text can be expressed as illustrated in FIG. 26B, FIG. 26C, orFIG. 26D. The expressed character and/or text disappear when apredetermined time elapses or a predetermined key is input.

FIG. 5 is a flowchart illustrating an operation for setting up arelation to a contact person who has made continuouscall/message-related contact (or registering the person in a specificgroup) using a character agent in accordance with an exemplaryembodiment of the present invention.

Referring to FIG. 5, an event collection unit (not illustrated) collectsa call (or phone call) and message-related contact events when the call(or phone call) and message-related contact events occur. The call (orphone call) and message-related contact events may be phone calltermination events, incoming phone call reception events, outgoing phonecall transmission events, message reception events, and/or messagetransmission events. Then, the call (or phone call) and message-relatedcontact events are provided to an event delivery unit (not illustrated).The event delivery unit (not illustrated) provides the events to aspecialist manager of an agent control unit in step 1802. The specialistmanager stores the call (or phone call) and message-related contactevents in a blackboard in step 1804. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen the call (or phone call) and message-related contact events occurin step 1806. Then, the specialist manager calls the specialists in step1808. (FIG. 5 illustrates an example in which a specialist of ID 6 iscalled.)

Among the called specialists, the specialist of ID 6 is provided to arecommend relation setup (or group registration) when a continuous call(or phone call) and/or message-related contact with a contact person hasbeen made, but a relation to the contact person (or his/her phonenumber) has not been set up (or the contact person (or his/her phonenumber) has not been registered in a specific group). In step 1812, thecall (or phone call) and/or message-related contact records for onerecent month are analyzed. Then, a determination is made as to whetherthe call (or phone call) and/or message-related contact with a contactperson (or his/her phone number) has been made at least a thresholdnumber of times (for example, at least seven times) for a predeterminedperiod (for example, one recent month) in step 1814. If continuouscontact with an associated contact person has not been made (at least athreshold number of times of at least seven times for a predeterminedperiod of one month), the operation proceeds to step 1814 to return the‘NO’ signal to the specialist manager. However, if continuous contactwith the associated contact person has been made, the operation proceedsto step 1816 to return the ‘YES’ signal. In step 1816, a determinationis made as to whether a relation to the contact person (or his/her phonenumber) has been set up or has been registered in a specific group). Ifthe relation setup (or group registration) has been made, the operationproceeds to step 1818 to return the ‘NO’ signal to the specialistmanager. However, if a relation to the contact person (or his/her phonenumber) has not been set up or has not been registered in a specificgroup, the operation proceeds to step 1820 to return the ‘YES’ signal tothe specialist manager.

When a called specialist makes the return, the specialist managerprovides a supervisor with an ID of the specialist returning the ‘YES’signal (for example, Specialist ID 6 of FIG. 5) in step 1822. Then, thesupervisor identifies priorities of associated specialists or identifiesthe execution of an associated specialist when the number of specialistsreturning the ‘YES’ signal is one in step 1824. In step 1826, thesupervisor sends, to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 1828 and sends the identified UI ID to an agent expression unitin step 1830. In step 1832, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of an associated contact person can also besent.

When this agent expression unit expresses a UI, for example, a UI mappedto Specialist ID 6, text for recommending the setup of a relation (orgroup) for an associated contact person of a call (or phone call) and/ormessage (or his/her phone number) can be included and expressed asillustrated in FIG. 27A. When an image and text for setting a characterwith a happy expression and/or a relation (or group) type are expressedand the relation (or group) is set up according to the user's feedbackas illustrated in FIG. 27B, a character with a happy expression and/ortext indicating that the associated contact person (or his/her phonenumber) will be registered are expressed as illustrated in FIG. 27C or acharacter with a sad expression and/or text indicating that theassociated contact person (or his/her phone number) will not beregistered are expressed as illustrated in FIG. 27D. When apredetermined time elapses or a predetermined key is input, theexpressed character and/or text disappear. The information of thecontact person includes a phone number and ID of the contact person whohas made the call and/or message-related contact.

In accordance with an exemplary embodiment of the present invention, arecommendation can be made for relation setup or group registrationassociated with a contact person who has made a regular call (or phonecall) and/or message-related contact (at least a threshold number oftimes per second predetermined period, for a first predeterminedperiod). For example, a determination is made as to whether the relationsetup (or group registration) for the contact person has been performedwhen the call (or phone call) and/or message-related contact with thecontact person has been made at least one time per week for one month.If the relation setup (or group registration) for the contact person hasnot been made, a character and/or text for recommending the relationsetup (or group registration) can be expressed.

FIG. 6 is a flowchart illustrating an operation for setting up an alarmfor recommending contact with a specific person who has previously maderegular contact, but has not recently made contact using a characteragent in accordance with an exemplary embodiment of the presentinvention.

Referring to FIG. 6, an event collection unit (not illustrated) collectsa call (or phone call) and message-related contact events when the call(or phone call) and message-related contact events occur. The call (orphone call) and message-related contact events may be phone calltermination events, incoming phone call reception events, outgoing phonecall transmission events, message reception events, and/or messagetransmission events. Then, the call (or phone call) and message-relatedcontact events are provided to an event delivery unit (not illustrated).The event delivery unit (not illustrated) provides the events to aspecialist manager of an agent control unit in step 1902. The specialistmanager stores the call (or phone call) and message-related contactevents in a blackboard in step 1904. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen the call (or phone call) and message-related contact events occurin step 1906. Then, the specialist manager calls the specialists in step1908. (FIG. 6 illustrates an example in which a specialist of ID 7 iscalled.)

Among the called specialists, the specialist of ID 7 is provided torecommend the call (or phone call) and/or message-related contact with acontact person (or his/her phone number) when a regular call (or phonecall) and/or message-related contact with the contact person (or his/herphone number) has been made at least a predetermined number of times persecond predetermined period, for a first predetermined period, but hasnot been made for the next third predetermined period. For example, thespecialist of ID 7 recommends the call (or phone call) and/ormessage-related contact with a contact person (or his/her phone number)when the regular phone call and/or message-related contact with thecontact person has been made at least a threshold number of times (forexample, at least one time) per second predetermined period (forexample, one week) for the first predetermined period (for example, onemonth), but has not been made for the next third predetermined period(for example, three weeks).

In step 1910, the specialist of ID 7 identifies the blackboard anddetermines if the regular call (or phone call) and/or message-relatedcontact with the associated contact person (at least the thresholdnumber of times per second predetermined period, for the firstpredetermined period). For example, the specialist of ID 7 determines ifthe regular call (or phone call) and/or message-related contact with theassociated contact person (or his/her phone number) has been made atleast one time per week for one month.

If the regular call (or phone call) and/or message-related contact withthe associated contact person has not been made (at least a thresholdnumber of times (for example, at least one time) per secondpredetermined period (for example, week) for the first predeterminedperiod (for example, one month) as a determination result, the operationproceeds to step 1912 to return the ‘NO’ signal to the specialistmanager. However, if regular call (or phone call) and/or message-relatedcontact with the associated contact person has been made (at least athreshold number of times (for example, at least one time) per secondpredetermined period (for example, week) for the first predeterminedperiod (for example, one month)) as a determination result, theoperation proceeds to step 1914. In step 1914, an alarm of ID 7 is setup. In the ID7 alarm setup, an alarm occurrence time (that is, apredetermined time after three weeks of the third predetermined periodfrom the ID7 alarm setup time) is set, and an associated contact personis registered for the ID7 alarm. If the ID7 alarm has been previouslyset up, the ID7 alarm time is reset to the next occurrence time. Then,the operation proceeds to step 1916 to return the ‘ID7 alarm setup’signal to the specialist manager. For example, the ‘ID7 alarm’ is set upand the ‘ID7 alarm setup’ signal is returned to the specialist managerwhen the call (or phone call) and/or message-related contact with theassociated contact person has been made at least one time in the firstweek of the month, at least one time in the second week of the month, atleast one time in the third week of the month, and at least one time inthe fourth week of the month.

When a called specialist (that is, the specialist of ID 7) makes thereturn, the specialist manager provides a supervisor with an ID of thespecialist returning the ‘YES’ signal. In FIG. 6, the number ofspecialists called at the time of a call (or phone call) and/ormessage-related contact event is one, corresponding to the specialist ofID 7, in accordance with an exemplary embodiment of the presentinvention. In this case, another specialist ID to be sent from thespecialist manager to the supervisor is absent because the associatedspecialist of ID 7 returns the ‘NO’ signal and the ‘ID7 alarm setup’signal. In an exemplary embodiment of the present invention, thespecialist can be configured such that it performs a suitable operationat the time of an associated call (or phone call) and/or message-relatedcontact event and returns the ‘YES’ signal. In this case, the specialistmanager can provide the supervisor with an ID of a specialist returningan associated ‘ID7 alarm setup’ signal. Then, the supervisor identifiespriorities of associated specialists or identifies the execution of anassociated specialist. The supervisor sends, to the specialist manager,a result of the identification for the highest priority specialist orthe execution of the associated specialist. Then, the specialist manageridentifies a UI ID of the highest priority specialist or the specialistto be executed and sends the identified UI ID to an agent expressionunit (not illustrated). The agent expression unit expresses anassociated UI (or alarm registration UI).

FIG. 7 is a flowchart illustrating an operation for recommending contactwith a specific person who has previously made regular contact but hasnot recently made contact using a character agent, in accordance with anexemplary embodiment of the present invention.

In FIG. 7, the specialist manager stores a received call (or phone call)and/or message-related alarm events in a blackboard in step 1952 whenreceiving the call (or phone call) and/or message-related alarm eventsin step 1950. Then, the specialist manager identifies specialists to becalled from an internal specialist list when the call (or phone call)and message-related alarm events occur in step 1954. Then, thespecialist manager calls the specialists in step 1956. (FIG. 7illustrates an example in which a specialist of ID 7 is called.)

The specialist of ID 7 called is provided to a recommend call (or phonecall) and/or message-related contact with an associated contact person(or his/her phone number) when regular contact with the contact personhas been made at least a predetermined number of times per secondpredetermined period, for a first predetermined period, but has not beenmade for the next third predetermined period.

Then, the specialist of ID 7 analyzes the call (or phone call) and/ormessage-related contact records through the blackboard and determines ifa regular call (or phone call) and/or message-related contact with theassociated contact person has been made (at least a threshold number oftimes per second predetermined period, for the first predeterminedperiod) and the contact with the associated contact person registeredfor the ID7 alarm event has been recently made at least a thresholdnumber of time (for example, at least one time) for three weeks of thethird predetermined period from the time of the ID7 alarm event setup.If the call (or phone call) and/or message-related contact with theassociated contact person has not been recently made at least athreshold number of times (for example, at least one time), theoperation proceeds to step 1960 to return the ‘YES’ signal to thespecialist manager. When the ‘YES’ signal is returned, information ofthe associated contact person can also be returned. For example, ifregular call (or phone call) and/or message-related contact with theassociated contact person has been made at least one time per week forthe last month, the ID7 alarm event has been set up, and the regularcontact with the associated contact person registered for the ID7 alarmevent has been recently made at least one time for three weeks from thetime of the ID7 alarm event setup, the ‘YES’ signal is returned to thespecialist manager.

If the call (or phone call) and/or message-related contact with theassociated contact person registered for the ID7 alarm event has beenrecently made at least a threshold number of time (for example, at leastone time) for three weeks of the third predetermined period from thetime of the ID7 alarm event setup as a determination result, theoperation proceeds to step 1964 to return the ‘NO’ signal to thespecialist manager.

When a called specialist (that is, the specialist of ID 7) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 1966. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 1968. In step 1970, thesupervisor sends, to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 1972 and sends the identified UI ID to the agent expression unitin step 1974. In step 1976, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of an associated contact person can also besent. When this agent expression unit expresses a UI, text for arecommending call (or phone call) and/or message-related contact with anassociated contact person (or his/her phone number) can be expressedalong with information of the associated contact person as illustratedin FIG. 28A. According to the user's feedback, text and/or a characterwith a happy expression are expressed for identifying acceptance of aphone call-related contact with the associated contact person (orhis/her contact information) as illustrated in FIG. 28B. According tothe user's feedback, text and/or a character with a happy expression areexpressed for identifying acceptance of message-related contact with theassociated contact person (or his/her contact information) asillustrated in FIG. 28C. According to the user's feedback, text and/or acharacter with a sad expression are expressed for identifying rejectionof phone call and message-related contact with the associated contactperson (or his/her contact information) as illustrated in FIG. 28D. Whena predetermined time elapses or a predetermined key is input, theexpressed character and/or text disappear.

In accordance with an exemplary embodiment of the present invention, theID7 alarm event may occur. First and second timers corresponding toreference time parameters are set in relation to a contact person (orhis/her phone number) such that a determination can be made as towhether the user has recently made much or little contact with thecontact person. When the call (or phone call) and/or message-relatedcontact with the contact person has not been made for periods set in thefirst and second timers, the ID7 alarm event occurs. However, when thecall (or phone call) and/or message-related contact with the contactperson has been made for the periods set in the first and second timers,the ID7 alarm event does not occur and the first and second set timersare deleted. When the call (or phone call) and/or message-relatedcontact with the contact person has been made for the periods set in thefirst and second timers, new first and second timers are set. Here, thefirst timer is used for the reference time for detecting the contactperson who has made little contact for a relatively short period forexample, one week), and the second timer is used for the reference timefor detecting the contact person who has made little contact for alonger period (for example, one month) than the first timer.

For example, if the first timer for the contact person's phone number of‘010-234-5673’ has timed out as a result of checking the timer at thecurrent reference time (for example, February 7), it means that thefirst timer has never been updated for one recent week (for example,February 1˜7). Accordingly, transmission to and reception from the phonenumber of the associated contact person has not been performed for onerecent week. In relation to the phone number of ‘010-234-5673’, thenumber of contact events for a period (for example, January 25˜31)before two weeks is compared with that of contact events for a period(for example, January 18˜24) before three weeks. According to a resultof the comparison, a determination is made as to whether little contactwith the associated contact person has been made. If the number ofcontact events for the period before the two weeks is a predeterminedratio, that is, 50%, less than that of contact events for the periodbefore three weeks, a determination is made that little contact with theassociated contact person has been made. If the second timer for thecontact person's phone number of ‘010-234-5673’ has timed out as aresult of checking the timer at the current reference time, it meansthat the second timer has never been updated for one recent month (forexample, March 1˜31). In this case, because a comparison associated withthe number of contact events for one recent month is not useful, thenumber of contact events before two months is compared with that ofcontact events before three months. If the user has made little contactwith the associated contact person as a result of the comparison, arecommendation for contact with a phone number of the associated contactperson is made and an associated second timer is deleted.

FIG. 8 is a flowchart illustrating an operation for recommending contactwith a specific person who has generally made little contact using acharacter agent in accordance with an exemplary embodiment of thepresent invention. Hereinafter, an ID8 alarm event may be set as adefault and may occur in a preset period. When call and message-relatedevents, such as a phone call transmission event, phone call receptionevent, message transmission event, and message read event occur, theoccurred events are collected and stored, and an associated alarm eventcan be set according to an occurred event. For example, when call andmessage-related events such as a phone call transmission event, phonecall reception event, message transmission event, and message read eventoccur, information of a specific person with whom contact has been madethrough the occurred call and message-related event is analyzed. The ID8alarm event can be set to recommend call or message-related contact witha specific person who has generally made little contact through the calland message-related event.

Referring to FIG. 8, the specialist manager stores a received alarmevent in the blackboard in step 2004 when the alarm event (for example,ID 8) is delivered in step 2002. Then, the specialist manager identifiesspecialists to be called from an internal specialist list when anassociated alarm event occurs in step 2006. Then, the specialist managercalls the specialists in step 2008. The called specialist of ID 8 isprovided to recommend phone call/message-related contact with a specificperson who has generally made little contact. For example, the alarm isreset, for example, after N days, in step 2010 (Alarm ID 8). This alarmreset is called and operated in a period of N (one month). For example,when the occurrence time of the alarm event is 2 p.m. on November 10 andthe period N is one month, the occurrence time of the next alarm eventis 2 p.m. on December 10.

Then, the specialist of ID 8 analyzes call (or phone call) and/ormessage-related event records, such as phone call transmission, phonecall reception, message transmission, and message reception through theblackboard, on a contact person-by-contact person basis in step 2012.That is, the specialist of ID 8 determines if a specific person who hasmade little contact for a recent period (one month) or information ofthe specific person is present by comparing the number of calls/messagesfor last month with that of calls/messages for this month on the contactperson-by-contact person basis, and determining if a comparison resultis less than a preset reference value. If the associated specific personis absent in step 2014, the operation proceeds to step 2016 to returnthe ‘NO’ signal to the specialist manager. However, if the associatedspecific person is present in step 2014, the operation proceeds to step2018 to return the ‘YES’ signal to the specialist manager. When the‘YES’ signal is returned, information of the specific person can also bereturned. Here, the information of the specific person indicates a phonenumber and ID of the specific person.

When a called specialist (that is, the specialist of ID 8) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 2020. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 2022. In step 2024, thesupervisor sends, to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 2026 and sends the identified UI ID to the agent expression unitin step 2028. In step 2030, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of an associated specific person can alsobe sent. When the agent expression unit expresses a UI, text forrecommending contact with the associated specific person as illustratedin FIG. 29A can be expressed along with the information of the specificperson. Here, if there are a number of associated specific persons,priorities of the specific persons are set and the text can recommendphone call/message-related contact with the specific person of thehighest priority or can recommend sequential contact with the specificpersons according to the priorities. Here, priorities are assigned on aphone number-by-phone number basis. For example, when it is assumed thatphone numbers of specific persons who have made little contact are phonenumbers of an elder brother and alumnus of an elementary school, thetext can recommend contact with the elder brother of the higher priorityusing his/her phone number.

According to the user's feedback, a character with a happy expressionand/or text are expressed for identifying acceptance of phonecall-related contact with the associated specific person (or his/herinformation) as illustrated in FIG. 29B. According to the user'sfeedback, a character with a happy expression and/or text are expressedfor identifying acceptance of message-related contact with theassociated specific person (or his/her information) as illustrated inFIG. 29C. According to the user's feedback, a character with a sadexpression and/or text are expressed for identifying rejection of phonecall and message-related contact with the associated specific person (orhis/her information) as illustrated in FIG. 29D. When a predeterminedtime elapses or a predetermined key is input, the expressed characterand/or text disappear.

FIG. 9 is a flowchart illustrating an operation for recommending contactwith a specific person of a specific group who has recently made littlecontact using a character agent in accordance with an exemplaryembodiment of the present invention. Hereinafter, an ID 10 alarm eventmay be set as a default and may occur in a preset period. When call andmessage-related events such as a phone call transmission event, phonecall reception event, message transmission event, and message read eventoccur, the occurred events are collected and stored, and an associatedalarm event can be set according to an occurred event. For example, whencall and message-related events such as a phone call transmission event,phone call reception event, message transmission event, and message readevent occur, information of a specific person with whom contact has beenmade through the occurred call and message-related event is analyzed.The ID10 alarm event can be set to recommend the call or message-relatedcontact with a specific person who has recently made little contactthrough the call and message-related event.

Referring to FIG. 9, the specialist manager stores a received alarmevent in the blackboard in step 2104 when the alarm event (for example,ID 10) is delivered in step 2102. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen an associated alarm event occurs in step 2106. Then, the specialistmanager calls the specialists in step 2108. The called specialist of ID10 is provided to recommend phone call/message-related contact with aspecific person of a specific group who has recently made littlecontact. Then, the alarm is reset, for example, after N days, in step2110 (Alarm ID 10). This alarm reset is called and operated in a periodof N (one week). For example, when the occurrence time of the alarmevent is 2 p.m. on November 10 and the period N is one week, theoccurrence time of the next alarm event is 2 p.m. on November 17.

Then, the specialist of ID 10 analyzes call (or phone call) and/ormessage-related contact records such as phone call transmission, phonecall reception, message transmission, and message reception through theblackboard on a contact person-by-contact person basis in the specificgroup in step 2112. That is, the specialist of ID 10 determines if aspecific person who has made little contact for a recent period (oneweek) or information of the specific person is present by determining ifthe number of calls/messages for one recent week is less than a presetreference value on the contact person-by-contact person basis in thespecific group. If the associated specific person is absent in step2114, the operation proceeds to step 2116 to return the ‘NO’ signal tothe specialist manager. However, if the associated specific person ispresent in step 2114, the operation proceeds to step 2118 to return the‘YES’ signal to the specialist manager. When the ‘YES’ signal isreturned, information of the specific person can also be returned. Here,the information of the specific person indicates a phone number and IDof the specific person.

When a called specialist (that is, the specialist of ID 10) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 2120. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 2122. In step 2124, thesupervisor sends, to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 2126 and sends the identified UI ID to the agent expression unitin step 2128. In step 2130, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of an associated specific person can alsobe sent. When the agent expression unit expresses a UI, text forrecommending phone call/message-related contact with the associatedspecific person as illustrated in FIG. 30(A) can be expressed along withthe information of the specific person. According to the user'sfeedback, a character with a happy expression and/or text are expressedfor identifying acceptance of phone call-related contact with theassociated specific person (or his/her information) as illustrated inFIG. 30B. According to the user's feedback, a character with a happyexpression and/or text are expressed for identifying acceptance ofmessage-related contact with the associated specific person (or his/herinformation) as illustrated in FIG. 30C. According to the user'sfeedback, a character with a sad expression and/or text are expressedfor identifying rejection of the phone call and message-related contactwith the associated specific person (or his/her information) asillustrated in FIG. 30D. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

FIG. 10 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this week using a character agent inaccordance with an exemplary embodiment of the present invention.Hereinafter, an ID39 alarm event may be set as a default and may occurin a preset period.

Referring to FIG. 10, the specialist manager stores a received alarmevent in the blackboard in step 2204 when the alarm event (for example,ID 39) is delivered in step 2202. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen an associated alarm event occurs in step 2206. Then, the specialistmanager calls the specialists in step 2208. The called specialist of ID39 is provided to give notification of the number of calls/messages forthis week. Then, the alarm is reset, for example, after N days (forexample, at 21:00 on Saturday of the next week), in step 2210 (Alarm ID39). This alarm reset is called and operated at 21:00 on Saturday of thenext week. Accordingly, the specialist of ID 39 is repeatedly called andoperated in a period of one week. For example, when the occurrence timeof the alarm event is 21:00 on Saturday, November 20 and the period N isone week, the occurrence time of the next alarm event is 21:00 onSaturday, November 27.

Then, the specialist of ID 39 analyzes call (or phone call) and/ormessage-related event records such as a phone call transmission, phonecall reception, message transmission, and message reception through theblackboard on a contact person-by-contact person basis in step 2212.That is, the specialist of ID 39 identifies, compares, and analyzesphone call transmission amounts, phone call reception amounts, messagetransmission amounts, and message transmission amounts for a firstpredetermined period (from 21:00 on Saturday, November 5, to 21:00 onSaturday, November 12, corresponding to a period of last week) and asecond predetermined period (from 21:00 on Saturday, November 12, to21:00 on Saturday, November 19, corresponding to a period of this week).Then, the ‘YES’ signal is returned to the specialist manager in step2214. When the ‘YES’ signal is returned, information of a result of thecomparison and analysis can also be returned.

When a called specialist (that is, the specialist of ID 39) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 2216. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 2218. In step 2220, thesupervisor sends to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 2222 and sends the identified UI ID to the agent expression unitin step 2224. In step 2226, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of a result of the associated comparisonand analysis can also be sent. When the agent expression unit expressesa UI, text for giving notification of the number of calls/messages forlast and this week as illustrated in FIG. 31 can be expressed along withthe information of the result of the associated comparison and analysis.

FIG. 11 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this month using a character agentin accordance with an exemplary embodiment of the present invention.Hereinafter, an ID40 alarm event may be set as a default and may occurin a preset period.

Referring to FIG. 11, the specialist manager stores a received alarmevent in the blackboard in step 2304 when the alarm event (for example,ID 40) is delivered in step 2302. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen an associated alarm event occurs in step 2306. Then, the specialistmanager calls the specialists in step 2308. The called specialist of ID40 is provided to give notification of the number of calls/messages forthis month. Then, the alarm is reset, for example, after N months (forexample, at 21:00 on the last day of the next month), in step 2310(Alarm ID 40). This alarm reset is called and operated at 21:00 on thelast day of the next month. Accordingly, the specialist of ID 40 isrepeatedly called and operated in a period of one month. For example,when the occurrence time of the alarm event is 21:00 on October 31 andthe period N is one month, the occurrence time of the next alarm eventis 21:00 on November 30.

Then, the specialist of ID 40 analyzes call (or phone call) and/ormessage-related event records such as phone call transmission, phonecall reception, message transmission, and message reception through theblackboard on a contact person-by-contact person basis in step 2312.That is, the specialist of ID 40 identifies, compares, and analyzesphone call transmission amounts, phone call reception amounts, messagetransmission amounts, and message transmission amounts for a firstperiod (from 21:00 on September 30 to 21:00 on October 31, correspondingto a period of last month) and a second period (from 21:00 on October 31to 21:00 on November 30, corresponding to a period of this month). Then,the ‘YES’ signal is returned to the specialist manager in step 2314.When the ‘YES’ signal is returned, information of a result of thecomparison and analysis can also be returned.

When a called specialist (that is, the specialist of ID 40) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 2316. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 2318. In step 2320, thesupervisor sends to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 2322 and sends the identified UI ID to the agent expression unitin step 2324. In step 2326, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of a result of the associated comparisonand analysis can also be sent. When the agent expression unit expressesa UI, text for giving notification of the number of calls/messages forthe last or this month can be expressed along with the information ofthe result of the associated comparison and analysis as illustrated inFIG. 32.

FIG. 12 is a flowchart illustrating an operation for giving notificationindicating if some work on today's TO-DO list has been completed using acharacter agent in accordance with an embodiment of the presentinvention. Hereinafter, an ID33 alarm event may be set as a default andmay occur in a preset period. The TO-DO list indicates today's workitems registered for a schedule management function. When some workregistered in the TO-DO list is performed, a result of executioncompletion can be automatically or manually recognized. For example,some work on the TO-DO list may be call and message-related events suchas an event for making phone call-related contact with a specific personat a specific time and an event for making message-related contact witha specific person at a specific time.

Referring to FIG. 12, the specialist manager stores a received alarmevent in the blackboard in step 2404 when the alarm event (for example,ID 33) is delivered in step 2402. Then, the specialist manageridentifies specialists to be called from an internal specialist listwhen an associated alarm event occurs in step 2406. Then, the specialistmanager calls the specialists in step 2408. The called specialist of ID33 is provided to give notification indicating if some work on today'sTO-DO list has been completed. Then, the alarm is reset, for example,after N days, in step 2410 (Alarm ID 33). This alarm reset is called andoperated in a period N of one day. For example, when the occurrence timeof the alarm event is 22:00 on November 10 and the period N is one day,the occurrence time of the next alarm event is 22:00 on November 11.Then, the specialist of ID 33 identifies today's TO-DO list through thememory or blackboard in step 2412. A determination is made as to whethersome work on the TO-DO list has been completed in step 2414. If anundone work item is absent in today's TO-DO list as a determinationresult, the operation proceeds to step 2416 to return the ‘NO’ signal tothe specialist manager. However, if the undone work item is present intoday's TO-DO list as a determination result, the operation proceeds tostep 2418 to return the ‘YES’ signal to the specialist manager. When the‘YES’ signal is returned, information of the undone work item of theTO-DO list can also be returned.

When a called specialist (that is, the specialist of ID 33) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 2420. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 2422. In step 2424, thesupervisor sends, to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 2426, and sends the identified UI ID to the agent expressionunit in step 2428. In step 2430, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of an undone work item of today's TO-DOlist can also be sent. When the agent expression unit expresses a UI,text for recommending a check of the information of the undone work itemof the TO-DO list as illustrated in FIG. 33A can be expressed along withthe information of the specific person. According to the user'sfeedback, a character with a happy expression and/or text are expressedfor identifying acceptance of a check of an undone work item of theTO-DO list as illustrated in FIG. 33B. According to the user's feedback,a character with a sad expression and/or text are expressed whichindicate that an undone work item of the TO-DO list has not been checkedas illustrated in FIG. 33C. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

FIG. 13 is a flowchart illustrating an operation for giving notificationindicating if some work on yesterday's TO-DO list has been completedusing a character agent in accordance with an exemplary embodiment ofthe present invention. Referring to FIG. 13, the specialist managerstores a received alarm event in the blackboard in step 2504 when thealarm event (for example, ID 34) is delivered in step 2502. Then, thespecialist manager identifies specialists to be called from an internalspecialist list when an associated alarm event occurs in step 2506.Then, the specialist manager calls the specialists in step 2508. Thecalled specialist of ID 34 is provided to give notification indicatingif some work on yesterday's TO-DO list has been completed. Then, thealarm is reset, for example, after N days, in step 2510 (Alarm ID 34).This alarm reset is called in a period N of one day and an associatedoperation is again performed at 8 a.m. on the next day. For example,when the occurrence time of the alarm event is 8 a.m. on November 10 andthe period N is one day, the occurrence time of the next alarm event is8 a.m. on November 11.

Then, the specialist of ID 34 identifies yesterday's TO-DO list throughthe memory or blackboard in step 2512. A determination is made as towhether some work on the TO-DO list has been completed in step 2514. Ifan undone work item is absent in yesterday's TO-DO list as adetermination result, the operation proceeds to step 2516 to return the‘NO’ signal to the specialist manager. However, if an undone work itemis present in yesterday's TO-DO list as a determination result, theoperation proceeds to step 2518 to return the ‘YES’ signal to thespecialist manager. When the ‘YES’ signal is returned, information ofthe undone work item of yesterday's TO-DO list can also be returned.

When a called specialist (that is, a specialist of ID 34) makes thereturn, the specialist manager provides the supervisor with an ID of thespecialist returning the ‘YES’ signal in step 2520. Then, the supervisoridentifies priorities of associated specialists or identifies theexecution of an associated specialist in step 2522. In step 2524, thesupervisor sends, to the specialist manager, a result of theidentification for the highest priority specialist or the execution ofthe associated specialist. Then, the specialist manager identifies a UIID of the highest priority specialist or the specialist to be executedin step 2526 and sends the identified UI ID to the agent expression unitin step 2528. In step 2530, the agent expression unit expresses anassociated UI. When the specialist manager sends the UI ID to the agentexpression unit, information of the undone work item of yesterday'sTO-DO list can also be sent. When the agent expression unit expresses aUI, text for recommending a check of the information of the undone workitem of yesterday's TO-DO list as illustrated in FIG. 34A can beexpressed along with the information of the specific person. Accordingto the user's feedback, a character with a happy expression and/or textare expressed for identifying acceptance of a check of the undone workitem of the TO-DO list has been accepted as illustrated in FIG. 34B.According to the user's feedback, a character with a sad expressionand/or text are expressed which indicate that the undone work item ofthe TO-DO list has not been checked as illustrated in FIG. 34C. When apredetermined time elapses or a predetermined key is input, theexpressed character and/or text disappear.

An operation for processing an application program-related event of awireless terminal on a specialist-by-specialist basis using a characteragent as described above can be performed. The overall operation forprocessing an application program-related event of the wireless terminalwill be described with reference to the accompanying drawings. Toimplement the present invention, the controller 100 controls a singleagent system without functional blocks and controls the memory 23 andthe display unit 27. In this case, the memory 23 can collect and storeevents occurring in the wireless terminal.

FIG. 14 is a flowchart illustrating an operation for setting up arelation to a contact person who has made a call/message-related contact(or registering the contact person in a specific group) in the wirelessterminal in accordance with an exemplary embodiment of the presentinvention. An operation for recommending relation setup (or registrationin a specific group) when frequent contact with the contact person (orhis/her phone number) has been recently made, but a relation to thecontact person (or his/her phone number) has not been set up or has notbeen registered in a specific group, will be described with reference toFIG. 14. When a call (or phone call) or message-related contact eventoccurs in idle mode in step 3002, the controller 100 identifies theoccurred event in step 3004 and proceeds to step 3006. Here, call (orphone call) and message-related contact events may be phone calltermination events, incoming phone call reception events, outgoing phonecall transmission events, message reception events, and/or messagetransmission events. When the phone call termination event occurs, step3002 may be a state of phone call connection mode.

In step 3006, the controller 100 analyzes call (or phone call) and/ormessage-related contact records for one recent week. In step 3008, thecontroller 100 determines if the call (or phone call) and/ormessage-related contact with a contact person (or his/her phone number)has been frequently made at least a threshold number of times (forexample, at least three times) for a predetermined period (for example,one recent week).

If the call (or phone call) and/or message-related contact with anassociated contact person (or his/her phone number) has not been made atleast a threshold number of times as a determination result in step3010, the controller 100 proceeds to the step for ending the operation.However, if contact with an associated contact person has been made atleast a threshold number of times as a determination result, theoperation proceeds to step 3012. In step 3012, the controller 100determines if relation setup (or registration in a specific group) hasbeen performed for the associated contact person (or his/her phonenumber) in a contact person list (for example, a phone number list or aphone book). If the associated contact person (or his/her phone number)has been registered in the contact person list (for example, a phonenumber list, phone book, or specific group) and a relation (or group)has been set up as a determination result, the controller proceeds tothe step for ending the operation. However, if the associated contactperson (or his/her phone number) has not been registered in a contactperson list (for example, a phone number list, phone book, or specificgroup) and a relation (or group) has not been set up as a determinationresult, the controller 100 detects that the contact person has not beenregistered in step 3014 and proceeds to step 3016. In step 3016, thecontroller 100 expresses a selection button list and expresses acharacter and text for recommending the setup of a relation (or group)for an associated contact person (or his/her phone number) of a call (orphone call) and/or message as illustrated in FIG. 25A.

When the user selects ‘YES’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3018 and then proceeds to step 3020 to express a feedback foraccepting the setup of a relation (or group) for an associated contactperson (or his/her phone number). The feedback for accepting the setupof a relation (or group) is expressed by a character with a happyexpression and/or an image and text for setting a relation (or group)type as illustrated in FIG. 25B. When the relation (or group) type isset, the controller 100 expresses a character with a happy expressionand/or text for identifying the setup of the relation (or group) for thecontact person (or his/her phone number) as illustrated in FIG. 25C.

When the user selects ‘NO’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3018 and then proceeds to step 3022 to express a feedback forrejecting the setup of a relation (or group) for an associated contactperson (or his/her phone number). The feedback for rejecting the setupof a relation (or group) is expressed by a character with a sadexpression and text indicating that a relation (or group) for thecontact person (or his/her phone number) has not been set up asillustrated in FIG. 25D. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

FIG. 15 is a flowchart illustrating an operation for notifying that asubstantial number of a call/message-related contact has been made inthe wireless terminal in accordance with an exemplary embodiment of thepresent invention. An operation for notifying that the substantialnumber of a call (or phone call) or message-related contact with acontact person has been made will be described with reference to FIG.15. When a call (or phone call) or message-related contact event occursin idle mode in step 3102, the controller 100 identifies the occurredevent in step 3104 and proceeds to step 3106. Here, call (or phone call)and message-related contact events may be phone call termination events,incoming phone call reception events, outgoing phone call transmissionevents, message reception events, and/or message transmission events.When the phone call termination event occurs, step 3102 may be a stateof phone call connection mode.

In step 3106, the controller 100 analyzes call (or phone call) and/ormessage-related contact records for one recent week. In step 3108, thecontroller 100 determines if call (or phone call) and/or message-relatedcontact with a contact person (or his/her phone number) has beenfrequently made at least a threshold number of times (for example, atleast three times) for a predetermined period (for example, one week).

If the call (or phone call) and/or message-related contact with anassociated contact person (or his/her phone number) has not been made atleast a threshold number of times as a determination result in step3110, the controller 100 proceeds to the step for ending the operation.However, if contact with the associated contact person has been made atleast a threshold number of times as a determination result, theoperation proceeds to step 3112. In step 3112, the controller 100identifies the associated contact person (or his/her information), andexpresses the selection button list and a character and text fornotifying that the number of call (or phone call) and/or message-relatedcontact events associated with the associated contact person (or his/herphone number) is large as illustrated in FIG. 26A.

When the user selects one item of the selection button list, thecontroller 100 detects the selected item in step 3114 and then proceedsto step 3116 to express a feedback according to a selection buttonselected by the user. For example, the controller 100 first expresses afeedback mapped to a ‘YES’ button by expressing a character with a happyexpression and text mapped thereto as illustrated in FIG. 26B when theuser selects ‘YES’ corresponding to Item No. 1 from the selection buttonlist. Second, the controller 100 expresses a feedback mapped to a‘Really?’ button by expressing a character with a happy expressionand/or text mapped thereto as illustrated in FIG. 26C when the userselects ‘Really?’ corresponding to Item No. 2 from the selection buttonlist. Third, the controller 100 expresses a feedback mapped to a ‘Cut itoff!’ button by expressing a character with an angry expression and/ortext mapped thereto as illustrated in FIG. 26D when the user selects‘Cut it off!’ corresponding to Item No. 3 from the selection buttonlist. When a predetermined time elapses or a predetermined key is input,the expressed character and/or text disappear.

FIG. 16 is a flowchart illustrating an operation for setting up arelation to a contact person who has made continuouscall/message-related contact (or registering the person in a specificgroup) in the wireless terminal in accordance with an exemplaryembodiment of the present invention. An operation for recommendingrelation setup (or group registration) when continuous call (or phonecall) and/or message-related contact with a contact person has been madebut a relation to the contact person (or his/her phone number) has notbeen set up or has not been registered in a specific group, will bedescribed with reference to FIG. 16. When a call (or phone call) ormessage-related contact event occurs in idle mode in step 3202, thecontroller 100 identifies the occurred event in step 3204 and proceedsto step 3206. Here, call (or phone call) and message-related contactevents may be phone call termination events, incoming phone callreception events, outgoing phone call transmission events, messagereception events, and/or message transmission events. When the phonecall termination event occurs, step 3202 may be a state of phone callconnection mode.

In step 3206, the controller 100 analyzes call (or phone call) and/ormessage-related contact records for one recent month. In step 3208, thecontroller 100 determines if the call (or phone call) and/ormessage-related contact with a contact person (or his/her phone number)has been frequently made at least a threshold number of times (forexample, at least seven times) for a predetermined period (for example,one month).

If call (or phone call) and/or message-related contact with anassociated contact person (or his/her phone number) has not been made atleast a threshold number of times as a determination result in step3210, the controller 100 proceeds to the step for ending the operation.However, if contact with the associated contact person has been made atleast a threshold number of times as a determination result, theoperation proceeds to step 3212. In step 3212, the controller 100determines if relation setup (or registration in a specific group) hasbeen performed for the associated contact person (or his/her phonenumber) in a contact person list (for example, a phone number list or aphone book). If the associated contact person (or his/her phone number)has been registered in a contact person list (for example, a phonenumber list, phone book, or specific group) and a relation (or group)has been set as a determination result, the controller 100 proceeds tothe step for ending the operation. However, if the associated contactperson (or his/her phone number) has not been registered in a contactperson list (for example, a phone number list, phone book, or specificgroup) and the relation (or group) has not been set as a determinationresult, the controller 100 detects that the contact person has not beenregistered in step 3214 and proceeds to step 3216. In step 3216, thecontroller 100 expresses a selection button list and expresses acharacter and text for recommending the setup of the relation (or group)for an associated contact person (or his/her phone number) of a call (orphone call) and/or message as illustrated in FIG. 27A.

When the user selects ‘YES’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3218 and then proceeds to step 3220 to express a feedback foraccepting the setup of the relation (or group) for an associated contactperson (or his/her phone number). The feedback for accepting the setupof the relation (or group) is expressed by a character with a happyexpression and/or an image and text for setting the relation (or group)type as illustrated in FIG. 27B. When the relation (or group) type isset, the controller 100 expresses a character with a happy expressionand/or text for identifying the setup of the relation (or group) for thecontact person (or his/her phone number) as illustrated in FIG. 27C.

When the user selects ‘NO’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3218 and then proceeds to step 3222 to express a feedback forrejecting the setup of the relation (or group) for an associated contactperson (or his/her phone number). The feedback for rejecting the setupof the relation (or group) is expressed by a character with a sadexpression and text indicating that the relation (or group) for thecontact person (or his/her phone number) has not been set up asillustrated in FIG. 27D. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

In accordance with an exemplary embodiment, a recommendation can be madefor relation setup or group registration associated with a contactperson who has made regular contact using a call (or phone call) and/ormessage (at least a threshold number of times per second predeterminedperiod for a first predetermined period). For example, a determinationis made as to whether the relation setup (or group registration) for thecontact person has been performed when a call (or phone call) and/ormessage-related contact with the contact person has been made at leastone time per week for one month. If the relation setup (or groupregistration) for the contact person has not been performed, a characterand/or text for recommending the relation setup (or group registration)can be expressed.

FIG. 17 is a flowchart illustrating an operation for setting up an alarmfor recommending contact with a specific person who has previously maderegular contact but has not recently made contact in the wirelessterminal in accordance with an exemplary embodiment of the presentinvention.

An operation for recommending contact with a specific person who hasmade regular contact using a call (or phone call) and/or message but hasnot recently made contact using the call (or phone call) and/or messagewill be described with reference to FIG. 17.

When the call (or phone call) or message-related contact event occurs inidle mode in step 3302, the controller 100 identifies the occurred eventin step 3304 and then proceeds to step 3306. Here, call (or phone call)and message-related contact events may be phone call termination events,incoming phone call reception events, outgoing call transmission events,message reception events, and/or message transmission events. When thephone call termination event occurs, step 3302 may be a state of a phonecall connection mode.

In step 3306, the controller 100 analyzes call (or phone call) and/ormessage-related contact records for one recent month. In step 3310, thecontroller 100 determines if a regular call (or phone call) and/ormessage-related contact with the associated contact person has been made(at least a threshold number of times per second predetermined periodfor the first predetermined period). For example, the controller 100determines if the regular call (or phone call) and/or message-relatedcontact with the associated contact person (or his/her phone number) hasbeen made at least one time per week for one month.

If the regular call (or phone call) and/or message-related contact withthe associated contact person has not been made (at least a thresholdnumber of times (for example, at least one time) per secondpredetermined period (for example, week) for the first predeterminedperiod (for example, one month) as a determination result, thecontroller 100 proceeds to the step for ending the operation. However,if the regular call (or phone call) and/or message-related contact withthe associated contact person (or his/her phone number) has been made(at least a threshold number of times (for example, at least one time)per second predetermined period (for example, week) for the firstpredetermined period (for example, one month)) as a determinationresult, the controller 100 proceeds to step 3312. In step 3312, thecontroller 100 sets up an alarm (or ID7 alarm) for recommending the call(or phone call) and/or message-related contact with a specific personwho has previously made regular contact using a call (or phone call)and/or message but has not recently made contact using a call (or phonecall) and/or message. In the ID7 alarm setup, an alarm occurrence time(that is, a predetermined time after three weeks of the thirdpredetermined period from the ID7 alarm setup time) is set, and anassociated contact person associated with the ID7 alarm is registered.If the ID7 alarm has been previously set up, the ID7 alarm time is resetto the next occurrence time. The predetermined time after the threeweeks may be a period of from a first predetermined time (for example,30 minutes) before the last contact event of a call (or phone call)and/or message occurs to the contact event time of the call (or phonecall) and/or message, a period of from the contact event time of thecall (or phone call) and/or message to a second predetermined time (forexample, 30 minutes) after the contact event of the call (or phone call)and/or message occurs, or a period of from the first predetermined timeto the second predetermined time. For example, the ‘ID7 alarm’ is set upbecause the call (or phone call) and/or message-related contact with theassociated contact person has been made at least one time in the firstweek of the month, at least one time in the second week of the month, atleast one time in the third week of the month, and at least one time inthe fourth week of the month.

FIG. 18 is a flowchart illustrating an operation for recommendingcontact with a specific person who has previously made regular contactbut has not recently made contact in the wireless terminal in accordancewith an exemplary embodiment of the present invention.

An operation for processing an alarm event for recommending a call (orphone call) and/or message-related contact with a specific person whohas previously made regular contact using a call (or phone call) and/ormessage, but has not recently made contact using a call (or phone call)and/or message will be described with reference to FIG. 18. When a call(or phone call) or message-related contact event occurs in idle mode instep 3320, the controller 100 identifies the present time in step 3322and proceeds to step 3324. In step 3324, the controller 100 identifiesthe occurrence time of the set ID7 alarm event (for recommending a call(or phone call) and/or message-related contact with an associatedcontact person (or his/her phone number) when regular contact with thecontact person has been made a predetermined number of times per secondpredetermined period, for a first predetermined period, but has not beenmade for a third predetermined period). If the present time correspondsto the occurrence time of the ID7 alarm event, the controller 100detects the time in step 3226 and then proceeds to step 3328. In step3328, the controller 100 analyzes call (or phone call) and/ormessage-related contact records. In step 3330, the controller 100determines if the call (or phone call) and/or message-related contactwith an associated contact person has been made for a predeterminedperiod (for example, the third predetermined period (three weeks) offrom the ID7 alarm setup time to the occurrence time of the ID7 alarmevent) before the occurrence time of the ID7 alarm event.

If a call (or phone call) and/or message-related contact with theassociated contact person has been made as a determination result, thecontroller 100 proceeds to the step for ending the operation. However,if the call (or phone call) and/or message-related contact with theassociated contact person has not been made as a determination result,the controller 100 proceeds to step 3332. In step 3332, the controller100 expresses a selection button list and expresses a character and textfor recommending call (or phone call) and/or message-related contactwith the associated contact person as illustrated in FIG. 28A.

When the user selects ‘Phone Call’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3334 and then proceeds to step 3336 to express a feedback foraccepting the phone call-related contact with the associated contactperson (or his/her contact information). The feedback for accepting thephone call-related contact is expressed by a character with a happyexpression and/or an image and text for identifying the acceptance ofthe phone call-related contact with the associated contact person (orhis/her contact information or phone number) as illustrated in FIG. 28B.

When the user selects ‘Message’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3338 and then proceeds to step 3340 to express a feedback foraccepting a message-related contact with the associated contact person(or his/her contact information). The feedback for accepting themessage-related contact is expressed by a character with a happyexpression and/or an image and text for identifying the acceptance ofthe message-related contact with the associated contact person (orhis/her contact information or phone number) as illustrated in FIG. 28C.

When the user selects ‘NO’ corresponding to Item No. 3 from theselection button list, the controller 100 proceeds to step 3342 toexpress a feedback for rejecting phone call and message-related contactwith the associated contact person (or his/her contact information). Thefeedback for rejecting the phone call and message-related contact isexpressed by a character with a sad expression and/or an image and textfor identifying the rejection of the phone call and message-relatedcontact with the associated contact person (or his/her contactinformation or phone number) as illustrated in FIG. 28D. When apredetermined time elapses or a predetermined key is input, theexpressed character and/or text disappear.

In accordance with an exemplary embodiment, the ID7 alarm event mayoccur. The controller 100 sets first and second timers corresponding toreference time parameters in relation to a contact person (or his/herphone number) such that a determination can be made as to whether muchor little contact with the contact person has been recently made. When acall (or phone call) and/or message-related contact with the contactperson has not been made for periods set in the first and second timers,the controller 100 generates the ID7 alarm event. However, when the call(or phone call) and/or message-related contact with the contact personhas been made for the periods set in the first and second timers, thecontroller 100 does not generate the ID7 alarm event, deletes the firstand second set timers, and sets new first and second timers when thecall (or phone call) and/or message-related contact with the contactperson has been made for the periods set in the first and second timers.Here, the first timer is used for the reference time for detecting thecontact person who has made little contact for a shorter period (forexample, one week) than that of the second timer, and the second timeris used for the reference time for detecting the contact person who hasmade little contact for a longer period (for example, one month) thanthat of the first timer.

For example, if the first timer for the contact person's phone number of‘010-234-5673’ has timed out as a result of checking the timer at thecurrent reference time (for example, February 7), it means that thefirst timer has never been updated for one recent week (of February1˜7). This means that transmission to and reception from the phonenumber of the associated contact person has not been performed for onerecent week. In relation to the phone number of ‘010-234-5673’, thenumber of contact events for a period (for example January 25˜31) beforetwo weeks is compared with that of contact events for a period (forexample January 18˜24) before three weeks. According to a comparisonresult, a determination is made as to whether little contact with theassociated contact person has been made. If the number of contact eventsfor the period before the two weeks is a predetermined ratio, that is,50%, less than that of contact events for the period before three weeks,a determination is made that little contact with the associated contactperson has been made. If the second timer for the contact person's phonenumber of ‘010-234-5673’ has timed out as a result of checking the timerat the current reference time, it means that the second timer has neverbeen updated for one recent month (for example, March 1˜31). In thisinstance, because a comparison associated with the number of contactevents for one recent month is not useful, the number of contact eventsbefore two months is compared with that of contact events before threemonths. If little contact with the associated contact person has beenmade as a comparison result, contact with a phone number of theassociated contact person is recommended and an associated second timeris deleted.

FIG. 19 is a flowchart illustrating an operation for recommendingcontact with a specific person who has generally made little contact inthe wireless terminal in accordance with an exemplary embodiment of thepresent invention. The operation for recommending contact with aspecific person who has generally made little contact will be describedwith reference to FIG. 19. When an alarm event occurs in idle mode instep 3402, the controller 100 detects the occurred alarm event in step3404 and then proceeds to step 3406. In step 3406, the controller 100analyzes the occurred alarm event and determines a type of alarm event.When the occurred alarm event is an ID8 alarm event for recommendingcontact with a specific person who has generally made little contact,the controller 100 detects the ID8 alarm event in step 3408 and thenproceeds to step 3410. In step 3410, the controller 100 resets theoccurrence time of the ID8 alarm event. This alarm reset is called andoperated in a period of N (one month). For example, when the occurrencetime of the alarm event is 2 p.m. on October 10 and the period N is onemonth, the occurrence time of the next alarm event is 2 p.m. on November10. The controller 100 analyzes and identifies phone call transmissionamounts, phone call reception amounts, message transmission amounts, andmessage transmission amounts on a contact person-by-contact person basisin step 3412. In step 3414, the controller 100 determines if a specificperson who has made little contact for a recent period N (one month) orinformation of the specific person is present by comparing the number ofcalls/messages for last month with that of calls/messages for this monthon the contact person-by-contact person basis, and determining if acomparison result is less than a preset reference value. Here, if thereare a number of associated specific persons, priorities of the specificpersons are set and the text can recommend phone call/message-relatedcontact with the specific person of the highest priority, or canrecommend sequential contact with the specific persons according to thepriorities. Here, priorities are assigned on a phone number-by-phonenumber basis. For example, when it is assumed that phone numbers ofspecific persons who have made little contact are phone numbers of anelder brother and an alumnus of an elementary school, the text canrecommend contact with the elder brother of the higher priority usinghis/her phone number.

When an associated specific person is present, the controller 100proceeds to step 3416. In step 3416, the controller 100 extractsinformation of the associated specific person, and expresses a selectionbutton list. At this time, a character and text for recommendingcall/message-related contact with the associated specific person asillustrated in FIG. 29A can be expressed along with the information ofthe specific person.

When the user selects ‘Phone Call’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3418 and then proceeds to step 3420 to express a feedback foraccepting phone call-related contact with the associated contact person(or his/her information). The feedback for accepting the phonecall-related contact is expressed by a character with a happy expressionand/or text for identifying the acceptance of the phone call-relatedcontact with the associated contact person (or his/her information) asillustrated in FIG. 29B.

When the user selects ‘Message’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3422 and then proceeds to step 3424 to express a feedback foraccepting the message-related contact with the associated contact person(or his/her information). The feedback for accepting the message-relatedcontact is expressed by a character with a happy expression and/or textfor identifying the acceptance of the message-related contact with theassociated contact person (or his/her information) as illustrated inFIG. 29C.

When the user selects ‘NO’ corresponding to Item No. 3 from theselection button list, the controller 100 proceeds to step 3426 toexpress a feedback for rejecting the phone call and message-relatedcontact with the associated contact person using his/her information.The feedback for rejecting the phone call and message-related contact isexpressed by a character with a sad expression and/or an image and textfor identifying the rejection of the phone call and message-relatedcontact with the associated contact person using his/her information asillustrated in FIG. 29D. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

FIG. 20 is a flowchart illustrating an operation for recommendingcontact with a specific person of a specific group who has recently madelittle contact in the wireless terminal in accordance with an exemplaryembodiment of the present invention. The operation for recommendingcontact with a specific person of a specific group who has recently madelittle contact will be described with reference to FIG. 20. When analarm event occurs in idle mode in step 3502, the controller 100 detectsthe occurred alarm event in step 3504 and then proceeds to step 3506. Instep 3506, the controller 100 analyzes the occurred alarm event anddetermines a type thereof. When the occurred alarm event is an ID10alarm event for recommending contact with a specific person of aspecific group who has recently made little contact, the controller 100detects the ID10 alarm event in step 3508 and then proceeds to step3510. In step 3510, the controller 100 resets the occurrence time of theID10 alarm event. This alarm reset is called and operated in a period ofN (one week). For example, when the occurrence time of the alarm eventis 2 p.m. on November 10 and the period N is one week, the occurrencetime of the next alarm event is 2 p.m. on November 17.

The controller 100 analyzes and identifies phone call transmissionamounts, phone call reception amounts, message transmission amounts, andmessage transmission amounts on a contact person-by-contact person basisin step 3512. In step 3514, the controller 100 determines if a specificperson who has made little contact for a recent period (one week) orinformation of the specific person is present by comparing the number ofcalls/messages for last week with that of calls/messages for this weekon the contact person-by-contact person basis and determining if acomparison result is less than a preset reference value.

When an associated specific person is present, the controller 100proceeds to step 3516. In step 3516, the controller 100 extractsinformation of the associated specific person, and expresses a selectionbutton list. At this time, a character and text for recommending a phonecall/message-related contact with the associated specific person asillustrated in FIG. 30A can be expressed along with the information ofthe specific person.

When the user selects ‘Phone Call’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3518 and then proceeds to step 3520 to express a feedback foraccepting phone call-related contact with the associated contact person(or his/her information). The feedback for accepting the phonecall-related contact is expressed by a character with a happy expressionand/or text for identifying the acceptance of the phone call-relatedcontact with the associated contact person (or his/her information) asillustrated in FIG. 30B.

When the user selects ‘Message’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3522 and then proceeds to step 3524 to express a feedback foraccepting message-related contact with the associated contact person (orhis/her information). The feedback for accepting the message-relatedcontact is expressed by a character with a happy expression and/or textfor identifying the acceptance of the message-related contact with theassociated contact person (or his/her information) as illustrated inFIG. 30C.

When the user selects ‘NO’ corresponding to Item No. 3 from theselection button list, the controller 100 proceeds to step 3526 toexpress a feedback for rejecting phone call and message-related contactwith the associated contact person (or his/her information). Thefeedback for rejecting the phone call and message-related contact isexpressed by a character with a sad expression and/or an image and textfor identifying the rejection of the phone call and message-relatedcontact with the associated contact person (or his/her information) asillustrated in FIG. 30D. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

FIG. 21 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this week in the wireless terminalin accordance with an exemplary embodiment of the present invention. Anoperation for comparing the number of calls/messages for this week withthat of calls/messages for last week and giving notification of thenumber of calls/messages for this week will be described with referenceto FIG. 21. When an alarm event occurs in idle mode in step 3602, thecontroller 100 detects the occurred alarm event in step 3604 and thenproceeds to step 3606. In step 3606, the controller 100 analyzes theoccurred alarm event and determines a type of alarm event. When theoccurred alarm event is an ID39 alarm event for giving notification ofthe number of calls/messages for this week, the controller 100 detectsthe ID39 alarm event in step 3608 and then proceeds to step 3610.

In step 3610, the controller 100 resets the occurrence time of the ID10alarm event after N weeks (for example, at 21:00 on Saturday of the nextweek). This alarm reset is called in a period of N and is operated at21:00 on Saturday of the next week. For example, when the occurrencetime of the alarm event is 21:00 on Saturday, November 20 and the periodN is one week, the occurrence time of the next alarm event is 21:00 onSaturday, November 27.

In step 3612, the controller 100 identifies, compares and analyzes phonecall transmission amounts, phone call reception amounts, messagetransmission amounts, and message transmission amounts for a period oflast week (that is, a first predetermined period) and a period of thisweek (that is, a second predetermined period). In step 3614, thecontroller 100 obtains information of a result of comparing andanalyzing phone call transmission amounts, phone call reception amounts,message transmission amounts, and message transmission amounts for theperiod of last week (that is, the first predetermined period) and theperiod of this week (that is, the second predetermined period), and thenexpresses the information of the result of the comparison and analysisin the form of a character, text and graph as illustrated in FIG. 31.The information of the result of the comparison and analysis can beexpressed in a numerical value. If the number of phone calls for thisweek is more than that of phone calls for last week, or the number ofmessages for this week is more than that of messages for last week, acharacter with a happy expression and text mapped can be expressed.However, if the number of phone calls for this week is less than that ofphone calls for last week, or the number of messages for this week isless than that of messages for last week, a character with a sadexpression and text mapped can be expressed. When a predetermined timeelapses or a predetermined key is input, the expressed character and/ortext disappear.

FIG. 22 is a flowchart illustrating an operation for giving notificationof the number of calls/messages for this month in the wireless terminalin accordance with an exemplary embodiment of the present invention. Anoperation for comparing the number of calls/messages for this month withthat of calls/messages for last month and giving notification of thenumber of calls/messages for this month will be described with referenceto FIG. 22. When an alarm event occurs in idle mode in step 3702, thecontroller 100 detects the occurred alarm event in step 3704 and thenproceeds to step 3706. In step 3706, the controller 100 analyzes theoccurred alarm event and determines a type of alarm event. When theoccurred alarm event is an ID40 alarm event for giving notification ofthe number of calls/messages for this month, the controller 100 detectsthe ID40 alarm event in step 3708 and then proceeds to step 3710. Instep 3710, the controller 100 resets the occurrence time of the ID40alarm event after N weeks (for example, 21:00 on the last day of thenext month). This alarm reset is called and operated in a period N ofone month and is called and operated at 21:00 on the last day of thenext month. Accordingly, the ID40 alarm event is repeatedly called andoperated in a period of one month. For example, when the occurrence timeof the alarm event is 21:00 on October 31 and the period N is one month,the occurrence time of the next alarm event is 21:00 on November 30.

In step 3712, the controller 100 identifies, compares and analyzes phonecall transmission amounts, phone call reception amounts, messagetransmission amounts, and message transmission amounts for a period oflast month (that is, a first predetermined period) and a period of thismonth (that is, a second predetermined period).

In step 3714, the controller 100 obtains information of a result ofcomparing and analyzing phone call transmission amounts, phone callreception amounts, message transmission amounts, and messagetransmission amounts for the period of last month (that is, the firstpredetermined period) and the period of this month (that is, the secondpredetermined period). The controller 100 then expresses the informationof the result of the comparison and analysis in the form of a character,text and graph as illustrated in FIG. 32. The information of the resultof the comparison and analysis can be expressed in a numerical value. Ifthe number of phone calls for this month is more than that of phonecalls for last month, or the number of messages for this month is morethan that of messages for last month, a character with a happyexpression and text mapped can be expressed. However, if the number ofphone calls for this month is less than that of phone calls for lastmonth or the number of messages for this month is less than that ofmessages for last month, a character with a sad expression and textmapped can be expressed. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

FIG. 23 is a flowchart illustrating an operation for giving notificationindicating if some work on today's TO-DO list has been completed in thewireless terminal in accordance with an exemplary embodiment of thepresent invention. The TO-DO list indicates today's work itemsregistered for a schedule management function. When some work registeredin the TO-DO list is performed, a result of execution completion can beautomatically or manually recognized. For example, some work on theTO-DO list may be event registration for making phone call-relatedcontact with a specific person at a specific time and event registrationfor making message-related contact with a specific person at a specifictime.

The operation for giving notification indicating if some work on today'sTO-DO list has been completed will be described with reference to FIG.23. When an alarm event occurs at a set specific time (of a firstspecific time, that is, 10 p.m.) today (that is, a first predeterminedtime) in idle mode in step 3802, the controller 100 detects the occurredalarm event in step 3804 and then proceeds to step 3806. In step 3806,the controller 100 analyzes the occurred alarm event and determines atype thereof. When the occurred alarm event is an ID33 alarm event forgiving notification indicating if some work on today's TO-DO list(mapped to the first predetermined period) has been completed, thecontroller 100 detects the ID33 alarm event in step 3808 and thenproceeds to step 3810. In step 3810, the controller 100 resets theoccurrence time of the ID33 alarm event. This alarm reset is called in aperiod N of one day and is operated at 22:00 on the next day. Forexample, when the occurrence time of the alarm event is 22:00 on October10 and the period N is one day, the occurrence time of the next alarmevent is 22:00 on October 11.

In step 3812, the controller 100 analyzes and identifies work itemsregistered in today's TO-DO list (mapped to the first predeterminedperiod). In step 3814, the controller 100 determines if an undone workitem of the work items registered in today's TO-DO list (mapped to thefirst predetermined period) is present. If an undone work item of thework items registered in today's TO-DO list (mapped to the firstpredetermined period) is present as a determination result, thecontroller 100 proceeds to step 3816. In step 3816, the controller 100extracts the undone work item of the TO-DO list, and expresses aselection button list and a character and text for recommending a checkof the undone work item of the TO-DO list as illustrated in FIG. 33A.

When the user selects ‘YES’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3818 and then proceeds to step 3820 to express a feedback foraccepting the check of the undone work item of the TO-DO list. Thefeedback for accepting the check of the undone work item of the TO-DOlist is expressed by a character with a happy expression and/or text foridentifying the acceptance of the check of the undone work item of theTO-DO list as illustrated in FIG. 33B.

When the user selects ‘NO’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3818 and then proceeds to step 3822 to express a feedback forrejecting the check of an undone work item of the TO-DO list. Thefeedback for rejecting the check of an undone work item of the TO-DOlist is expressed by a character with a sad expression and/or textindicating that the undone work item of the TO-DO list has not beenchecked as illustrated in FIG. 33C. When a predetermined time elapses ora predetermined key is input, the expressed character and/or textdisappear.

FIG. 24 is a flowchart illustrating an operation for giving notificationindicating if some work on yesterday's TO-DO list has been completed inthe wireless terminal in accordance with an exemplary embodiment of thepresent invention. The operation for giving notification indicating ifsome work on yesterday's TO-DO list has been completed will be describedwith reference to FIG. 24. When an alarm event occurs at a set specifictime (of a second specific time, that is, 8 a.m.) today in idle mode instep 3902, the controller 100 detects the occurred alarm event in step3904 and then proceeds to step 3906. In step 3906, the controller 100analyzes the occurred alarm event and determines a type of alarm event.When the occurred alarm event is an ID34 alarm event for givingnotification indicating if some work on yesterday's TO-DO list (mappedto a first predetermined period) has been completed, the controller 100detects the ID34 alarm event in step 3908 and then proceeds to step3910. In step 3910, the controller 100 resets the occurrence time of theID34 alarm event. This alarm reset is called in a period N of one dayand is operated at 8 a.m. on the next day. For example, when theoccurrence time of the alarm event is 8 a.m. on November 10 and theperiod N is one day, the occurrence time of the next alarm event is 8a.m. on November 11.

In step 3912, the controller 100 analyzes and identifies work itemsregistered in yesterday's TO-DO list (mapped to the first predeterminedperiod). In step 3914, the controller 100 determines if an undone workitem of the work items registered in yesterday's TO-DO list (mapped tothe first predetermined period) is present. If an undone work item ofthe work items registered in the TO-DO list, yesterday's TO-DO list(mapped to the first predetermined period) is present as a determinationresult, then the controller 100 proceeds to step 3916. In step 3916, thecontroller 100 extracts the undone work item of the TO-DO list, andexpresses a selection button list and a character and text forrecommending a check of the undone work item of the TO-DO list asillustrated in FIG. 34A.

When the user selects ‘YES’ corresponding to Item No. 1 from theselection button list, the controller 100 detects the selected item instep 3918 and then proceeds to step 3920 to express a feedback foraccepting the check of an undone work item of the TO-DO list. Thefeedback for accepting the check of the undone work item of the TO-DOlist is expressed by a character with a happy expression and/or text foridentifying the acceptance of the check of the undone work item of theTO-DO list as illustrated in FIG. 34B.

When the user selects ‘NO’ corresponding to Item No. 2 from theselection button list, the controller 100 detects the selected item instep 3918 and then proceeds to step 3922 to express a feedback forrejecting the check of an undone work item of the TO-DO list. Thefeedback for rejecting the check of an undone work item of the TO-DOlist is expressed by a character with a sad expression and/or textindicating that the undone work item of the TO-DO list has not checkedas illustrated in FIG. 34C. When a predetermined time elapses or apredetermined key is input, the expressed character and/or textdisappear.

In accordance with exemplary embodiments of the present invention asdescribed above, a character agent function is added to a wirelessterminal and an avatar user interface (UI) for generating and processingan event, is expressed when an event occurs in the wireless terminal,such that call and message-related events occurring in the wirelessterminal can be expressed through the character agent function.

In accordance with the embodiment of the present invention as describedabove, an operation for processing a phone call/message-related eventcan be performed in the wireless terminal. While the invention has beenshown and described with reference to certain exemplary embodimentsthereof, it will be understood by those skilled in the art that variouschanges in form and details may be made therein without departing fromthe spirit and scope of the invention as defined by the appended claims.

What is claimed is:
 1. A method for processing events for a wirelessterminal, the method comprising: in response to an occurrence of acommunication event at the wireless terminal, determining whether anumber of the occurred communication event is more than a thresholdnumber; determining identification information related to thecommunication event, if the number of the occurred communication eventis more than the threshold number; and displaying a user interface (UI)for recommending registering the identification information to a user ofthe wireless terminal if the identification information relating to thecommunication event is not registered.
 2. The method of claim 1, furthercomprising: providing an indication of the occurrence of thecommunication event.
 3. The method of claim 1, further comprising:determining whether the identification information associated with thecommunication event is the registered identification information.
 4. Themethod of claim 1, wherein the displaying of the UI for the recommendingof registering the identification information occurs in response todetermining that the identification information associated with thecommunication event is not registered identification information.
 5. Themethod of claim 1, further comprising: receiving an indication whetherto register the identification information.
 6. The method of claim 5,wherein the indication corresponds to selection of a button on the UIassociated with registering identification information.
 7. The method ofclaim 5, further comprising: registering, in the event that theindication whether to register the identification informationcorresponds to an indication that the identification information is tobe registered, the identification information as registeredidentification information.
 8. The method of claim 1, wherein thedisplaying of the UI for the recommending of registering theidentification information comprises displaying, on the UI, a button toadd the identification information.
 9. The method of claim 1, whereinthe registered identification information corresponds to identificationinformation that is associated with a user profile of the user.
 10. Themethod of claim 1, further comprising: detecting the occurrence of thecommunication event.
 11. An apparatus for processing events for awireless terminal, the apparatus comprising: in response to anoccurrence of a communication event at the wireless terminal, one ormore controllers operatively configured to: determine whether a numberof the occurred communication event is more than a threshold number;determine identification information related to the communication event,if the number of the occurred communication event is more than thethreshold number; and control a display unit to display a user interface(UI) for recommending registering the identification information to auser of the wireless terminal if the identification information relatingto the communication event is not registered.
 12. The apparatus of claim11, wherein the one or more controllers are further operativelyconfigured to provide an indication of the occurrence of thecommunication event.
 13. The apparatus of claim 11, wherein the one ormore controllers are further operatively configured to determine whetherthe identification information associated with the communication eventis the registered identification information.
 14. The apparatus of claim11, wherein the one or more controllers are further operativelyconfigured to display the UI for the recommending of registering theidentification information in response to determining that theidentification information associated with the communication event isnot registered identification information.
 15. The apparatus of claim11, wherein the one or more controllers are further operativelyconfigured to receive an indication whether to register theidentification information.
 16. The apparatus of claim 15, wherein theindication corresponds to selection of a button on the UI associatedwith registering the identification information.
 17. The apparatus ofclaim 15, wherein the one or more controllers are further operativelyconfigured to register the identification information as the registeredidentification information in the event that the indication whether toregister the identification information corresponds to an indicationthat the identification information is to be registered.
 18. Theapparatus of claim 11, wherein the one or more controllers are furtheroperatively configured to display the identification information bydisplaying, on the UI, a button to add the identification information.19. The apparatus of claim 11, wherein the registered identificationinformation corresponds to identification information that is associatedwith a user profile of the user.
 20. The apparatus of claim 11, whereinthe one or more controllers are further operatively configured to detectthe occurrence of the communication event.